BBS Toolkit/BBS Toolkit.iso/programs/xrs510.zip/XRS51DOC.ZIP/REQUIRED.RAM

Text File | 1992-08-08 | 6KB | 93 lines

PLEASE READ THIS THOROUGHLY BEFORE ATTEMPTING TO CHANGE ANY OF THE PRE-DEFINED
 DEFAULT RUN-TIME MEMORY ALLOCATIONS THAT XRS AUTOMATICALLY USES BY DEFAULT!!

XRS is compiled into only two versions, now.  These are equivalent in function
(and name) to the previous RESP_OVL.EXE and RESP_RTL.EXE versions, but include
corresponding RESP*.DLL files instead of RESP*.OVL files.  IN EVERY CASE, THE
corresponding RESP*.DLL file is =Required= for execution! (Even if you do not
use them in "Overlayed mode"!)

If you have a machine with no LIM/EMS or XMS (extended) memory, simply use the
new RESPONSE.BAT and RESP_286.BAT files included to force XRS to run all in
conventional memory just like the versions with those names used to run! (you
do not need to read further - just type RESPONSE or RESP_286 to start up XRS.)
NOTE THAT THIS DEFEATS THE NORMAL OVERLAYING, AND LEAVES LESS MEMORY TO RUN!

 ================ Fine-tuning the run-time memory allocation ================

 Beginning with v 4.52, XRS is linked with PocketSoft's "RTLink+ 5.x" linker.
 This linker provides extreme flexibility both for the developer and the end
 user for running the programs linked with RTLink+ in conventional (low 640K
 RAM), expanded or XMS (extended) memory.  The developer (me) sets defaults
 for the optimal memory utilization for 90% of the users but end-users (you)
 can use environment variables to fine-tune or even detune my intentions.

 You can fine tune my run-time caching to better suit your own computer if you
 think my defaults are not optimal for your situation (I chose 128K of EMS or
 XMS memory for caching by default - up to this amount will be used if it is
 available), or if your computer's implementation of LIM/EMS memory is not
 100% compatible.  You can "SET RTOVEMS=xx,yy" to control EMS memory caching.
 'xx' is decimal (you could use "xx%" to express it as percentage of available
 memory).  The second "yy" parameter is a "Minimum to Leave" which is optional
 and can be used to keep run-time caching from completely using all EMS or XMS
 memory if you have a certain requirement due to other programs, etc.  Again,
 the optional 'minimum to leave' parameter can be decimal "K" or a percentage.
 "SET RTOVEXT=xx,yy" operates exactly the same for XMS cache sizing.  Some
 examples: "SET RTOVEMS=128,256" would allow up to 128K to be used, but not
 leaving less than 256K free.  "SET RTOVEXT=64,20%" would use 64K as long as
 that doesn't exceed 20% of the total XMS memory available.  Also, another
 variable "SET RTOVCONV=xxx,yyy" allows you to allocated a portion of the low
 (640K) RAM for caching.  Example: "SET RTOVCONV=120,120" uses up to 120K for
 caching, but never more memory than would leave 120K free for XRS to use.
 Note that any conventional memory allocated for caching is allocated from the
 top of the 640K RAM but is available (freed) during swapped shell-to-dos.

 The RESPONSE.BAT and RESP_286.BAT files work by turning off expanded/extended
 caching and caching in low (640K) "conventional" memory instead, then running
 the program - reseting (removing) the environment settings on exit.  (these
 files are in their respective XRS5xx?T.ZIP archives, and should replace any
 previous versions of these files you have)

OK - before you go hosing things up, read the following!  I don't want to have
to spend hours (days?!) explaining this over and over in the echo...  If what
you end up doing doesn't work well - try again - or just leave things alone!

In any case - read the following notes:

 Note 1: Most of you probably don't need to and never should adjust these!
   (other than possibly using "RESP*.BAT" as described above...)

 Note 2: RTLink+ startup will use _up_to_ the amount specified (whichever is
   less if both parameters are used) - it uses less if less if available,
   but never more than the maximum or more than would leave the minimum.  It
   will automatically use a combination to a total of 160K of EMS and XMS
   memory if there is less than 160K of EMS available.  EMS is preferred,
   because overlays can actually execute from expanded memory!

 Note 3: Cache "Hit" rates go down slowly when using slightly less memory,
   but the program will "thrash" excessively if you set it too low!

 Note 4: Optimal setting of these parameters varies widely depending upon the
   CPU (80386/486 is much faster, of course!) and rating/speed of the disk.
   If you change computers, you likely want to reevaluate these settings.

 Note 5: You must *NEVER* set conventional memory to less than 2K, since a
   small 2K block of the lower 640K must be used for bookkeeping purposes!

 Note 6: You should always try to set up a total of 144K of one or more types
   of memory for caching.  You *can* divide the cache between expanded and
   either of the other types of memory, or even use all three.  Using less
   than 100K will severaly impact program performance (i.e. it will run at a
   noticably overlayed-like speed).

 Note 7: LIM/EMS (and XMS memory provided by a 386/486 control program such
   as Quarterdeck's "QEMM386.SYS" or Qualitas' "386^Max" which always provide
   LIM and XMS memory from the same pool) is allocated in "chunks" of 16K.
   If you specify a non-16K multiple it is always rounded up to the next 16K.

 Note 8: Remember - I said you can use this to "Detune" my optimal selections
   as well.  If you pick a truly bad combination, you will know it, because
   the program will execute slowly, very slowly or not well at all.  If you
   are not certain you need to adjust these, leave them alone!  If you have
   160K free LIM/EMS 3.2 or later RAM, you should not adjust them, either...